AArch64 built and runs fine, so building the rest now.

Alright, the upcoming LLVM 19 release builds and works fine. @truboxl, @licy183 and @TomJo2000, you may want to start trying to build the rust, zig, and flang compilers with these new packages: simply download the zip file from the CI and unpack the .deb packages to ~/.termux-build/_cache-aarch64/ or whichever arch you need, so you don't have to waste time rebuilding LLVM.

I just need to update the llvm-config script for the CI and this should be ready to go for the initial patch release, but I won't merge till the compilers that dynamically link against it are ready. Swift statically links its own forked LLVM, so there's no need to bump that package and a couple others that do the same.

LLVM 19.1.0 will be released in the next couple days. I see only two compilers that dynamically link against it and which would break on the update: crystal and rust.

@HertzDevil, do you know if crystal will rebuild fine against the next LLVM release? @truboxl, get a chance to try rebuilding rust yet with this update?

We have a pending PR for Crystal that was last known to work with some x86-64 Debian release after 19.1.0-rc1. Our next minor release is scheduled for Oct 9th, although that PR needs to land before 25th this month. I do not believe there are any AArch64-specific blockers.

I do not understand what makes this branch so special that ./scripts/buildorder.py really unhappy.
Keeps spawning undeterministic errors below, preventing me to build other packages:

ERROR: Package binutils-is-llvm depends on non-existing package "llvm"
ERROR: Package binutils-is-llvm depends on non-existing package "lld"

EDIT: ah might be the blacklist arch

ah might be the blacklist arch

Yeah, just remove that line. I didn't want to rebuild AArch64 unnecessarily, as I had already built it first.

Rust should be ready for LLVM 19 with next version 1.82, scheduled for October 17: https://releases.rs/docs/1.82.0/

That's way too long, is there a LLVM 19 pull we can backport instead?

Rebased to fix CI issues

That's way too long, is there a LLVM 19 pull we can backport instead?

We can try build rust 1.82.0 beta but I have no idea why the build broke.

error: manifest path `mdbook-spec/Cargo.toml` does not exist
error: failed to extract std links (ExitStatus(unix_wait_status(32512)))

I am surprised the Rust team is waiting so long after the initial LLVM 19 patch release to support it. It would be better if there's an upstream pull you could backport to 1.81. I think somebody did that before for us and it wasn't a massive patch or anything, but I didn't look closely.